Skip to main content
Check and provide your planning data

BETA This is a new service – your feedback will help us to improve it.

Back to dataset table
East Hampshire District Council

Tree

There is a problem

  • 1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1036

reference
422-tree-1
name
1036
tree-preservation-order

undefined

422-tpo-1
uprn
address-text
point
POINT (-1.011322 50.890937)
geometry
MULTIPOLYGON (((-1.011251 50.890930,-1.011255 50.890944,-1.011264 50.890956,-1.011280 50.890966,-1.011300 50.890973,-1.011321 50.890975,-1.011343 50.890973,-1.011363 50.890967,-1.011379 50.890957,-1.011390 50.890945,-1.011393 50.890931,-1.011390 50.890917,-1.011380 50.890904,-1.011365 50.890894,-1.011345 50.890888,-1.011323 50.890885,-1.011301 50.890887,-1.011281 50.890894,-1.011265 50.890903,-1.011255 50.890916,-1.011251 50.890930)))
notes
felled-date
entry-date
2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL